Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[uss_qualifier] extract some fragments for scenarios injecting flights #892

Merged
merged 1 commit into from
Jan 22, 2025

Conversation

Shastick
Copy link
Contributor

#880 will add a scenario that does some flight injections, and we start to have some duplicated steps and checks.

This PR proposes to move common steps and checks to their own fragment.


## 🛑 Identifiable flights check

This particular test requires each flight to be uniquely identifiable by its 2D telemetry position; the same (lat, lng) pair may not appear in two different telemetry points, even if the two points are in different injected flights. This should generally be achieved by injecting appropriate data.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not within scope of this PR: No requirement specified here?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I did not design the original test, so I'm not sure.

Possibly the scenario could check this and abort/skip the run if the condition is not met instead?

@Shastick Shastick force-pushed the net0320-factor-out-injection branch 2 times, most recently from 15f8daf to 8e5aad2 Compare January 21, 2025 16:36
@Shastick Shastick requested a review from mickmis January 21, 2025 17:04
@Shastick Shastick force-pushed the net0320-factor-out-injection branch from 8e5aad2 to bfcc4f4 Compare January 22, 2025 07:06
@mickmis mickmis merged commit 9ad12cf into interuss:main Jan 22, 2025
20 checks passed
@mickmis mickmis deleted the net0320-factor-out-injection branch January 22, 2025 11:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants